2015-12-27 - 23845 - Service Request - SNC Inbound Delivery #MMPPSupport #sncsup

2015-12-27 - 23845 - Service Request - SNC Inbound Delivery


Problem Summary


The SNC Inbound Delivery creation program takes almost 3 hours to run. Please review to see if it can be improved.

Admin Info


Purpose
SNC Inbound Delivery
Requested by
Jeffrey Mau
Issue Date
12/27/2015
Resolved by
Damodhier,Adithya,Karthikeyan
Resolved Date
01/18/2016
Document Status
Complete

Detailed Problem Description

(Include Screen Shots if required )

The Inbound Delivery program is taking long time to run. Which is one of the most time taking programs in the Production server.

Estimates


Sl.No
Activity
Estimation in Hours
1
Research

2
Documentation
08
3
Development/ Config
12
4
Unit test in DEV
12
5
Unit test in QUA

6
Other activity


TOTAL
32
Solution Analysis and Recommendations
(Include Screen Shots if required)

Analyzed the program and understand that the program is considering all the SNC POs(giving the vendor number as input) from EKKO table and it is processing the logic on all the POs.
Here are couple of things which we can do to improve the performance:
1. We can add a check to filter the POs which are completed with GR.
2. Optimize the program technically by changing the statements.
Approximately the expected performance improvement of the program may be 10 to 30 %.

Currently we can do above two things and we will work on creating Inbound Deliveries for NB and Z3NB POs at once as the EKES table is huge and the data retrieving for two Pos at once may be delayed.

Resolution

Change the program to optimize the program and also filter the GRed POs

The solution is to start the logic with the table EKES and then move to EKKO~EKPO~EKET~EKES and create the Inbound Deliveries, by giving the date range as input.

Notes


If MIGO is manually done on a PO having ZNEC confirmation key Inb delivery would not be created for that PO Eg: 4500125308 from NEP.
(if the confirmation key is ZSNC it would require Inb Delivery to do MIGO)
l.No
Activity
Estimation in Hours
1
Research
08
2
Documentation
08
3
Development/ Config
20
4
Unit test in DEV
20
5
Unit test in QUA
20
6
Other activity


TOTAL
76